This is based on Debug.debugPrintEnv

There's TypeUtils.findRootTypeId already, I wonder if that could cover this use case? It works on type_expr though.

Its full type is

TypeUtils.findRootTypeId ~(full : full) ~(env : QueryEnv.t) (t : Types.type_expr)

with type full = {extra: extra; file: File.t; package: package} and

type extra = {
  internalReferences: (int, Location.t list) Hashtbl.t;
  externalReferences:
    (string, (string list * Tip.t * Location.t) list) Hashtbl.t;
  fileReferences: (string, LocationSet.t) Hashtbl.t;
  mutable locItems: locItem list;
}

So my first question is would I need to build an extra value or would a dummy value like the following work?

{internalReferences: Hashtbl.empty, externalReferences: Hashtbl.empty, fileReferences: Hashtbl.empty, locItems: []}

As for getting type_expr values instead of Hover.extractedType values, I would need to modify Hover.findRelevantTypesFromType right? Or do you think I should be able to convert an extractedType to a type_expr?

type extractedType = {
  name: string;
  path: Path.t;
  decl: Types.type_declaration;
  env: SharedTypes.QueryEnv.t;
  loc: Warnings.loc;
}

Let's stick with your current approach!